home *** CD-ROM | disk | FTP | other *** search
-
-
-
- CCCCIIIIDDDD((((4444FFFF)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccceeeemmmmbbbbeeeerrrr 5555,,,, 1111999999994444)))) CCCCIIIIDDDD((((4444FFFF))))
-
-
-
- NNNNAAAAMMMMEEEE
- cid - Caller-ID access control list
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- The _H_y_l_a_F_A_X configuration parameter QQQQuuuuaaaalllliiiiffffyyyyCCCCIIIIDDDD specifies
- whether or not the identity of an inbound call should be
- checked against an access control list before the telephone
- is answered. If a modem is attached to a phone line that
- has Caller-ID service, and QQQQuuuuaaaalllliiiiffffyyyyCCCCIIIIDDDD is non-null, then only
- the callers identified in the file specified by the string
- (typically eeeettttcccc////cccciiiidddd) will be answered.
-
- Patterns are specified one per line and must conform to the
- regular expressions syntax specified by POSIX 1003.2; see
- _r_e__f_o_r_m_a_t(7). Comments may be included; they are introduced
- with the ``#'' character and extend to the end of the line.
- Any trailing white space on a line is ignored (for
- convenience when comments are used).
-
- If a line begins with ``!'', then the regular expression
- identifies callers that should be _r_e_j_e_c_t_e_d; otherwise
- regular expressions identify clients whose calls should be
- _a_c_c_e_p_t_e_d. The order of patterns in a CID file is important.
- When a call is to be answered, the _f_a_x_g_e_t_t_y process will
- compare the phone number presented by the modem against the
- patterns in the access control list in the order in which
- they appear in the file. The first pattern that matches the
- client's number is used to decide whether to accept or
- reject the call. If no patterns match the phone number then
- the call is not answered. Thus if you want to accept all
- but a restricted set of calls, the last line in the file
- should be ``^.*$''.
-
- Note that regular expression patterns should be written to
- match a phone number exactly. That is, patterns should be
- of the form:
- ^<pattern>$
-
- where the ``^'' and ``$'' characters are used to specify the
- start and end of the matching phone number. Additionally,
- regular expression patterns should handle white space that
- may appear in known locations. For example,
- ^([+]1){1}[ .-]*415[ .-]*555[ .-]*1212.*$
-
- matches the following phone number strings:
- +1.415.555.1212
- 415 555 1212
- 1-415-555-1212
-
- Finally, note that regular expressions can be used to
- specify many numbers with one pattern.
-
-
- Page 1 (printed 6/24/99)
-
-
-
-
-
-
- CCCCIIIIDDDD((((4444FFFF)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((DDDDeeeecccceeeemmmmbbbbeeeerrrr 5555,,,, 1111999999994444)))) CCCCIIIIDDDD((((4444FFFF))))
-
-
-
- NNNNOOOOTTTTEEEESSSS
- The caller's telephone number is recognized by using the
- CCCCIIIIDDDDNNNNuuuummmmbbbbeeeerrrr configuration parameter described in _c_o_n_f_i_g(4F).
- This parameter must be present in the per-modem
- configuration file for Caller-ID screening to function
- properly. If QQQQuuuuaaaalllliiiiffffyyyyCCCCIIIIDDDD is defined, but no CCCCIIIIDDDDNNNNuuuummmmbbbbeeeerrrr is
- specified, then no phone numbers will be recognized and all
- incoming calls will be ignored.
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- _f_a_x_g_e_t_t_y(1M), _c_o_n_f_i_g(4F), _r_e__f_o_r_m_a_t(7).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 2 (printed 6/24/99)
-
-
-
-